RFC - Request for Comments - Alphabetical Order
5
A
B
C
D
E
F
G
H
- Handling of Bi-directional Texts in MIME
- Harvard's network RJE (rfc499)
- Heafner, J.F ,McKenzie, A.M , Melvin, J.T , Sundberg, R.L , Watson, R.W , White, J.E.Data Transfer Protocol (rfc264)
- Heafner, J.F ,McKenzie, A.M , Melvin, J.T , Sundberg, R.L , Watson, R.W , White, J.E.File Transfer Protocol (rfc265)
- Hebrew Character Encoding for Interne Messages
- Helminthiasis of the Internet
- HEMS monitoring and control language
- HEMS monitoring and control language
- HEMS variable definitions
- High-level Entity Management Protocol HEMP
- High-level Entity Management System HEMS
- High-level framework for network-based resource sharing
- Hitchhikers guide to the Internet
- Host Access Protoco specification
- Host Access Protocol (HAP) Specification - Version 2
- Host accounting and administrative procedures (rfc136)
- Host address changes involving Rand and ISI (rfc404)
- Host Anycasting Service
- Host extensions for IP multicasting
- Host extensions for IP multicasting
- Host extensions for IP multicasting
- Host Group Extensions for CLNP Multicasting
- Host groups: A multicast extension to theInternet Protocol
- Host mnemonics proposed in RFC 226 NIC 7625 (rfc239)
- Host Monitoring Protocol
- Host names on-line (rfc608)
- Host names on-line
- Host Resources MIB
- Host software (rfc9)
- Host software (rfc2)
- Host software (rfc1)
- Host status (rfc597)
- Host-dependent FTP parameters (rfc480)
- Host-host control message formats
- Host-Host Protocol for an ARPANET-type network (rfc714)
- Host-IMP interface
- Host/IMP interface documentation (rfc209)
- Hostname Server
- Hostnames Server
- Hosts using the IMP Going Down message (rfc548)
- How to Use Anonymous FTP
- HPN Working Group Input to the IPng Requirements Solicitation
I
J
K
L
- Language-machine for data reconfiguration (rfc83)
- Latest network maps (rfc616)
- Leaving well enough alone (rfc686)
- Letter to all TIP users (rfc365)
- Letter to TIP users-2 (rfc386)
- Level 0 Graphic Input Protocol (rfc336)
- Level III Server Protocol for the Lincoln Laboratory NIC 360/67 Host (rfc109)
- Line Printer Daemon Protocol
- Link 191 (rfc104)
- Link number assignments
- Link usage violation (rfc417)
- List of NWG/RFC's 1-80 (rfc84)
- Listserv Distribute Protocol
- Loader Debugger Protocol
- Locating on-line documentation at SRI-ARC (rfc544)
- Logger Protocol error (rfc79)
- Logger Protocol proposal (rfc98)
- Logical message synchronization (rfc58)
- London node is now up (rfc588)
- Lost message detection (rfc534)
- Lost message detection (rfc516)
- Lost message detection and recovery protocol
M
- M.I.T
- Mail Box Protocol (rfc196)
- Mail Monitoring MIB
- Mail priority (rfc577)
- Mail retrieval via FTP (rfc458)
- Mail routing and the domain system
- Mail Transfer Protocol
- Mail Transfer Protocol
- Mail Transfer Protocol: ISI TOPS20 file definitions
- Mail Transfer Protocol: ISI TOPS20 implementation
- Mail Transfer Protocol: ISI TOPS20 MTP-NIMAILinterface
- Mail transition plan
- Maintenance of duplicate databases (rfc677)
- Management Information Base for Frame Relay DTEs
- Management Information Base for Network Management of TCP/IP-based internets
- Management Information Base for network management of TCP/IP-based internets
- Management Information Base for Network Management of TCP/IP-based internets: MIB-II
- Management Information Base for Network Management of TCP/IP-based internets: MIB-II
- Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)
- Manager to Manage Management Information Base
- Mapping between full RFC 822 and RFC 822 with restricte encoding
- Mapping between X.400 (1988) / ISO 10021 and RFC 822
- Mapping between X.400 and RFC 822
- Mapping between X.400 and RFC-822 Message Bodies
- Mapping between X.400(1984/1988) and Mail-11 (DECne mail)
- Mapping between X.400(1988) / ISO 10021 and RFC 822
- Mapping between X.400(1988) / ISO 10021 and RFC 822
- Market Viability as a IPng Criteria
- MARS - a Message Archiving and Retrieval Service
- Mathematical software on the ARPA Network (rfc382)
- McKenzie, A.M ,Melvin, J.T , Sundberg, R.L , Watson, R.W , White, J.E Revision of theMail Box Protocol (rfc278)
- Mean round-trip times in the ARPANET (rfc619)
- Measured performance of the Network Time Protocol in th Internet system
- Measurement of host costs for transmitting network data (rfc392)
- Media Type Registration Procedure
- Meeting announcement to discuss a network mail system (rfc453)
- Memo from the Consortium for Slow Commotion Research (CSCR)
- Memo to FTP group: Proposal for File Access Protocol (rfc520)
- Memorandum: Date change of mail meeting (rfc456)
- Message data types (rfc42)
- Message Posting Protocol (MPP)
- Message Send Protocol
- Message Send Protocol
- Message Transmission Protocol (rfc680)
- Message-ID numbers (rfc533)
- Mid-Level Networks: Potential Technical Services
- Migrating from X.400(84) to X.400(88)
- Military supplement to the ISO Transport Protocol
- MILNET name domain transition
- MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing theFormat of Internet Message Bodies
- MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text
- MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format ofInternet Message Bodies
- MIME Content Type for BinHex Encoded Files
- MIME Encapsulation of EDI Objects
- MIME Encapsulation of Macintos files - MacMIME
- Minor pitfall in the Telnet Protocol
- Minutes of Network Graphics Group meeting, 15-1 July 1973 (rfc549)
- Minutes of Network Working Group meeting, 5/1 through 5/19/71 (rfc164)
- MIT-MATHLAB meets UCSB-OLS -an example o resource sharing (rfc525)
- MIX and MIXAL at UCSB (rfc485)
- MIX and MIXAL? (rfc473)
- MLTNET: A (rfc339)
- Modeling and Simulation Requirements for IPng
- Models of policy based routing
- Modem Management Information Base (MIB) using SMIv2
- Modifications to RFC 177 (rfc181)
- Modifications to the Telnet specification (rfc562)
- Modularity and efficiency in protocol implementation
- More comments on the forthcoming protocol
- More fault tolerant approach to address resolution for a Multi-LAN system of Ethernets
- More on lost message detection (rfc512)
- More on standard host names (rfc273)
- MOSPF: Analysis and Experience
- MSDTP-Message Services Data Transmission Protocol
- Multi-LAN address resolution
- Multi-network broadcasting within the Internet
- Multi-site data collection facility
- Multicast Extensions to OSPF
- Multicast Transport Protocol
- MULTICS address change (rfc590)
- MULTICS sampling timeout change (rfc450)
- Multimedia mail meeting notes
- Multimedia mail meeting notes
- Multiprotocol Encapsulation over ATM Adaptation Laye 5
- Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode
- Multiprotocol Interconnect over Frame Relay
- Multiprotocol Interconnect over Frame Relay
- Multiprotocol Interoperability In IPng
- Mutual Encapsulation Considered Dangerous
N
- NADF Standing Documents: A Brief Overview
- NADF Standing Documents: A Brief Overview
- Name, addresses, ports, and routes
- NAME/FINGER Protocol
- Naming and Structuring Guidelines for X.500 Directory Pilots
- Naming Guidelines for Directory Pilots
- Naming Guidelines for the AARNet X.500 Directory Service
- NBMA Address Resolution Protocol (NARP)
- NCP statistics (rfc388)
- NCP status report: UCSB/Rand (rfc78)
- NCP survey (rfc460)
- NCP, ICP, and Telnet: The Terminal IMP implementation (rfc215)
- NCP/TCP transition plan
- NETBANK (rfc408)
- NETBLT: A bulk data transfer protocol
- NETBLT: A bulk data transfer protocol
- NETBUGGER3 (rfc162)
- NETCRT - a character display protocol (rfc205)
- NETED: A common editor for the ARPA network
- NETRJS Protocol
- NETRJS: A third level protocol for Remote JobEntry (rfc88)
- NETRJT: Remote Job Service Protocol for TIPS (rfc283)
- Network 10 Considered Harmful (Some Practices Shouldn't be Codified)
- Network Access to Multimedia Information
- Network activity report: UCSB Rand (rfc113)
- Network and data sharing bibliography (rfc243)
- Network and Infrastructure User Requirements for Transatlantic Research Collaboration - Brussels, July 16-18, and Washington July 24-25, 1990
- Network checkout (rfc193)
- Network checkpoint (rfc214)
- Network connectivity: A response to RFC 603 (rfc613)
- Network data management committee meeting announcement (rfc173)
- Network Debugging Protocol
- Network Fortran subprograms (rfc119)
- Network graphic attention handling (rfc178)
- Network graphics (rfc285)
- Network graphics loader (rfc186)
- Network Graphics meeting (rfc246)
- Network Graphics meeting (rfc134)
- Network Graphics Working Group meeting (rfc314)
- Network Graphics Working Group meeting - second iteration (rfc396)
- Network host status (rfc315)
- Network host status (rfc266)
- Network host status (rfc298)
- Network host status (rfc326)
- Network host status (rfc332)
- Network host status (rfc344)
- Network host status (rfc366)
- Network host status (rfc376)
- Network host status (rfc293)
- Network host status (rfc353)
- Network host status (rfc252)
- Network host status (rfc267)
- Network host status (rfc319)
- Network host status (rfc367)
- Network host status (rfc370)
- Network host status (rfc362)
- Network host status (rfc342)
- Network host status (rfc330)
- Network host status (rfc306)
- Network host status (rfc288)
- Network Information Center schedule for network users (rfc223)
- Network journal submission and delivery (rfc543)
- Network library information system (rfc286)
- Network logical map (rfc432)
- Network mail meeting summary (rfc469)
- Network mail path service
- Network make-work (rfc514)
- Network meeting (rfc99)
- Network meeting (rfc75)
- Network meeting (rfc35)
- Network meeting
- Network meeting epilogue, etc
- Network meeting notes (rfc82)
- Network meeting report (rfc77)
- Network News Transfer Protocol: Proposed Standard for the Stream-Based Transmission ofNews
- Network on-line operators (rfc121)
- Network PL1 subprograms (rfc120)
- Network questionnaires (rfc459)
- Network Remote Job Entry program - NETRJS (rfc325)
- Network requirements for scientific research: Internet task force on scientific computing
- Network Services Monitoring MIB
- Network specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB (rfc105)
- Network specifications for UCSB's Simple-Minded File System (rfc122)
- Network Standard Data Specification syntax (rfc645)
- Network subsystem for time sharing hosts
- Network Time Protocol (NTP) over the OSI Remote Operations Service
- Network Time Protocol (v3)
- Network Time Protocol NTP
- Network Time Protocol version 1 specification and implementation
- Network Time Protocol version 2 specification and implementation
- rfc4 Network timetable
- Network UNIX
- Network use on May 8 (rfc334)
- Network Working Group meeting (rfc85)
- Network Working Group meeting schedule (rfc234)
- Network/440 protocol concept (rfc187)
- New console attachments to the USCB host (rfc311)
- New DNS RR Definitions
- New Host-Host Protocol
- New interface - IMP/360 (rfc335)
- New MULTICS network software features (rfc411)
- New protocol is coming
- NFILE - a file access protocol
- NFS: Network File System Protocol specification
- NIC - third level ideas and other noise (rfc66)
- NIC course (rfc276)
- NIC distribution of manuals and handbooks (rfc185)
- NIC name server - a datagram-based information utility
- NIC NCP experiment (rfc550)
- NIC user directories at SRI ARC (rfc621)
- NIC view of standard host names (rfc237)
- NICNAME/WHOIS
- NICNAME/WHOIS
- NLS classes at network sites (rfc488)
- No high link numbers
- NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist (``NOC TT REQUIREMENTS'')
- Nonstandard for transmission of IP datagrams over serial lines: SLIP
- Note on interprocess communication in a resource sharing computer network (rfc60)
- Note on padding (rfc70)
- Note on protoco synch sequences (rfc529)
- Note on Reconnection Protocol (rfc671)
- Note on socket number assignment
- Note to protocol designers and implementers
- Notes on a conversation with Bob Kahn on the ICCC (rfc372)
- Notes on the Network Working Group meeting, Urbana, Illinois, February 17, 1971 (rfc101)
- Novell IPX Over Various WAN Media (IPXWAN)
- Novell IPX Over Various WAN Media (IPXWAN)
- Novell IPX Over Various WAN Media (IPXWAN)
- November, 1974, survey of New-Protocol Telnet servers (rfc669)
- NSFNET backbone SPF based Interior Gateway Protocol
- NSFNET routing architecture
- NTP PICS PROFORMA For the Network Time Protocol Version 3
- NW meeting on network usage (rfc212)
O
P
Q
R
S
T
U
V
W
X
Other
- [Ad hoc Telnet Protocol] (rfc318)
- [Letter from Feinroth re: NYU, ANL, and LB entering the net, and FTP protocol] (rfc551)
- [Link assignments]
- [Referring to NWG/RFC 11]